🤖 fix: clear stale usage state when history is rewritten so the next send does not auto-compact - #3818

…oundary

Start Here (replaceHistory), /reset (resetContext), and /clear
(truncateHistory) rewrite history to a fresh context boundary but left the
session's in-memory lastUsageState from the previous stream intact. The next
sendMessage fed that stale high usage into the on-send compaction check and
synthesized a spurious /compact request against the already-cleared context.

Clear the session usage state in all three paths; the next send re-seeds
accurate usage from post-boundary history.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

…st bootstrap

CI-only failure on this PR: 35 AgentListItem/GitStatusIndicatorView/
TaskGroupListItem tests failed with "Cannot access 'DragPreviewImage' before
initialization". Changing test files shifts bun's CI discovery order, letting
a pre-existing order bug surface: files that tear down with
`globalThis.document = undefined` poison installDom()'s snapshot/restore,
which propagates a document-less environment (with baseline observers
present) to later files; @react-dnd/asap then crashes at module eval and
leaves react-dnd's internal exports in TDZ, so every later import including
`?real=1` re-evals fails.

Fix at the chokepoint in tests/ui/dom.ts: the uninstaller re-bootstraps a
baseline when it would restore a poisoned document, and react-dnd's module
graph is evaluated eagerly while the DOM is healthy so re-evals resolve
initialized internals. Both guards in tests/ui/domIsolation.test.ts fail
against their own toggle.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

tests/ui/domIsolation.test.ts uses bun:test (it guards bun's single-process
module cache behavior), so the Jest-based integration run fails to resolve
its import. Skip it via testPathIgnorePatterns like the storybook bun tests.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

…ider usage

Codex P2: for a partial /clear, clearing the in-memory usage cache was
ineffective because the retained newest assistant row still carries
pre-truncation contextUsage and partial truncation appends no boundary, so
seedUsageStateFromHistory() restored the same stale value on the next send.

clearUsageState() now also suppresses history seeding until the provider
reports fresh usage (updateUsageStateFromModelUsage resets the flag). Guard
tests: a baseline proving the boundary-less fixture seeds, and a suppression
test that fails without the new guard.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

Codex P2: tests/ui/domIsolation.test.ts was excluded from Jest but no bun
target ran it, so the guards never executed in local validation or CI. Add
the file to the Makefile test-unit bun invocation and to the CI Unit job's
explicit file list.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

Codex P2: the in-memory seeding suppression does not survive an app restart.
After a partial /clear plus restart, seedUsageStateFromHistory() reloaded the
retained assistant row's pre-truncation contextUsage and could spuriously
auto-compact again.

Sanitize at the source: the partial-truncation rewrite now strips
contextUsage and contextProviderMetadata from retained rows, since those
snapshots measured a context that no longer exists. Restart-safe with no
extra persisted state; the in-memory suppression flag still covers the
same-process window until fresh provider usage arrives. Red-green verified
via a historyService test.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

Codex P2: queued user input rolls back an undispatched heartbeat reset
boundary and restores the pre-reset provider context, but the seeding
suppression from the boundary append stayed active, so the queued turn could
not recover the restored history's near-limit usage and skipped on-send
compaction. Re-enable seeding on successful rollback. Guard test drives the
real append -> queue -> rollback path and fails without the re-enable.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

Codex P2: when a partial truncation committed but the monitor-wake
restoration step of clearHistoryWithRetiredBashMonitorWakes threw, the
invalidation after the wrapper never ran and the session kept its
pre-truncation usage. Move the clear into the truncate closure, immediately
after the successful rewrite. Guard test injects a wake-restore failure and
fails without the move.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

Codex P2: message edits truncate a suffix, so the retained prefix's persisted
contextUsage still describes the active context. Blanket seeding suppression
meant an edit whose stream failed before reporting usage left the next send
unable to recover that valid snapshot, bypassing on-send compaction for
near-limit prefixes. clearUsageState() gains a preserveHistorySeeding option
used by the edit path. Guard test drives edit-then-send and fails without it.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

…st boundary

Codex P2: after a compaction boundary exists, a 25/50/75% truncation can
remove only sealed pre-boundary rows, leaving the active provider context
unchanged; stripping retained contextUsage and suppressing the in-memory
seed then discarded a valid near-limit snapshot and could skip required
on-send compaction.

truncateHistory now reports whether the cut reached the active window
(removed the latest durable boundary or later rows). Rows are sanitized and
session usage cleared only in that case. Red-green: forcing the flag true
fails the new preserve test; the strip test still guards boundary-less cuts.

---

_Generated with `mux` • Model: `anthropic:claude-fable-5` • Thinking: `xhigh`_

<!-- mux-attribution: model=anthropic:claude-fable-5 thinking=xhigh -->

…leave renderer ghost rows

truncateHistory/clearHistory now take an onRowsDeleted callback fired
with each committed step's deleted sequences, even when a later step
fails. The three DeleteMessage emitters (truncateHistory, destructive
replaceHistory, exec hard-restart clear) emit accumulated committed
deletions on failure paths too, so rows already removed from disk
cannot linger in the renderer with sequences no retry can report.

…tripping usage while the hazard exists

The copied prefix is written with usage snapshots stripped while the
archive still exists, so a failed or crashed archive removal leaves
nothing stale for a fresh session to seed. Once the removal commits the
hazard is gone, and a restore write brings the usage back because it is
exact for the restored prefix and an edited near-limit prefix must stay
monitored on the next send.

…after the rewrite

The edit-truncation commit callback now reports whether the retained
rows' persisted usage stays valid. Active-file suffix cuts create no
duplicated prefix, so seeding re-enables at commit and a near-limit
prefix stays monitored despite the Err; the archived branch keeps
suppression until full success.

Use target-state hashes to distinguish committed and interrupted archive rewrites, recover legacy tombstones, and serialize logical reads with recovery.

Generated with mux • Model: openai:gpt-5.6-sol • Thinking: xhigh

<!-- mux-attribution: model=openai:gpt-5.6-sol thinking=xhigh -->

Let usage rebuilds iterate history through the lock-held path so transaction recovery remains serialized without reacquiring the shared non-reentrant mutex.

Generated with mux • Model: openai:gpt-5.6-sol • Thinking: xhigh

<!-- mux-attribution: model=openai:gpt-5.6-sol thinking=xhigh -->

Recover pending archive transactions and capture chat plus sealed history atomically before writing the fork session files.

Generated with mux • Model: openai:gpt-5.6-sol • Thinking: xhigh

<!-- mux-attribution: model=openai:gpt-5.6-sol thinking=xhigh -->